What we shipped, and why

Recurring events now recompute every occurrence against the zone rather than the offset, which means a weekly call booked in March stays at the same local hour on both ends when daylight saving moves.

• Recurring occurrences store a zone, not an offset
• A warning appears when a series crosses a transition
• Existing series are migrated on first edit

Anyone opening your booking page can now connect their own calendar and see it laid over your free times. Nothing is stored, nothing is shared with you — the overlay is drawn in their browser and forgotten when they close the tab.

Ask up to five questions before a booking, and send the answer to whichever calendar should have it. A question can branch, and a branch can end in a different event type with different availability.

• Short answer, choice and yes-or-no questions
• Branch on any answer
• Answers arrive in the calendar invite

When an event type has a price, the slot is held for fifteen minutes while the payment completes, instead of being released the moment the visitor leaves the page. Failed payments release it immediately.

Round-robin now balances by how many meetings each person has actually taken this month, not by whose turn it is in a list. Collective availability finds the hour that everyone shares, including people whose working hours differ.

• Fairness-weighted round-robin
• Collective availability across mixed working hours
• Shared event types with one owner

The embed now reports its own height to the host page, so the booking page grows and shrinks in place instead of sitting inside a box with its own scrollbar. One line of markup, unchanged.